Skip to content

fix(gates): verify_multitarget killed 0 of 7 — the same mistake, twice (#2492) - #2544

Merged
gHashTag merged 3 commits into
masterfrom
fix/multitarget-verdict-2
Aug 23, 2026
Merged

gHashTag merged 3 commits into
masterfrom
fix/multitarget-verdict-2

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Re-opened from #2541, which received 7 checks where a sibling opened minutes earlier received 35. emit-bitexact did not run despite tools/verify_multitarget.py being explicitly listed in its pull_request paths; an empty commit did not re-trigger it; and a second branch touching the same files got a normal check list. The cause was that pull request, not the paths. Not diagnosed — re-opened rather than merged without checks.


verify_multitarget.py scored 0 killed of 7, with survivor lines identical in shape to verify_emit_bitexact.py's (#2538): the gate's own sys.exit(0 if ok else 1) under both return operators, and all three comparison FAIL branches under inversion.

Both controls cover the skip pair. Both leave through skip() and never reach main(). Two gates, one mistake, made twice — the second time three iterations after writing down the first.

The plant moves one arm: py_ref reads the Python model while C and Rust come from t27c, so perturbing it makes the model disagree with backends that are unchanged. Perturbing the spec or the emitter would move every arm together and plant nothing.

Result: 0/7 → 5/7, only boundary survivors left.

Refs #2492

Re-opened from #2541, whose pull request received 7 checks where a
sibling opened minutes earlier received 35 -- emit-bitexact did not run
despite tools/verify_multitarget.py being explicitly listed in its
pull_request paths. An empty commit did not re-trigger it, and a second
branch touching the SAME files got a normal check list, so the cause was
that pull request rather than the paths.

Not diagnosed. Re-opened rather than merged without checks.
@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-23 12:42:43 UTC

Summary

Status Count
Total Open PRs 8
PRs with Failing Checks 4
PRs with All Checks Green 4
READY 3
FAILING 4
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e905ba8eeb53 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-23 13:01:45 UTC

Summary

Status Count
Total Open PRs 8
PRs with Failing Checks 4
PRs with All Checks Green 4
READY 3
FAILING 4
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e905ba8eeb53 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag

Copy link
Copy Markdown
Collaborator Author

Blocked on coverage, which is failing on master as well — the last two master runs of both coverage and Corpus ratchet are failures, so neither red is introduced here. emit-bitexact, the job that runs the changed file, completed success.

Not merging with --admin: overriding branch protection is a repository decision, not mine to take unilaterally. Leaving this open rather than forcing it.

@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-23 13:40:27 UTC

Summary

Status Count
Total Open PRs 7
PRs with Failing Checks 3
PRs with All Checks Green 4
READY 3
FAILING 3
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=e905ba8eeb53 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 456c6b0 into master Aug 23, 2026
25 of 26 checks passed
@gHashTag
gHashTag deleted the fix/multitarget-verdict-2 branch August 23, 2026 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant